Communication system and method

ABSTRACT

A communication system is disclosed. In an embodiment, the communication system includes a user node for receiving data from a remote application program, the data including message data for communication to a central application program operatively associated with the remote application program; plurality of geographically distributed gateway nodes; one or more access nodes for receiving the message data from the user node via a first communications interface, and communicating the message data via a second communications interface to one or more of the plurality of geographically distributed gateway nodes; and a hub for communicating with the one or more of the plurality of geographically distributed gateway nodes to receive the message data for communication to the central application.

TECHNICAL FIELD

The present invention relates to a communication system and method. In atypical application, an embodiment of the present invention may provideservices for supporting data communication between remotely deployedequipment and a control and management system via a satellite basedaccess node.

BACKGROUND

Providing two-way data communications to remote sensors and devices isbecoming increasingly critical for a wide range of applications. Costeffective communications to terrestrial and maritime field sensors, andindustrial automation and control equipment, for example, has thepotential to deliver significant economic and environmental benefits inareas such as environmental monitoring for climate change, water,mining, agriculture, defence and national security.

Many high-value applications have modest data rate requirements(kilobits per second), and can tolerate intermittent communications withlatency up to several hours. Frequently such applications involvesensors in very remote areas where terrestrial communication solutionsdo not exist, are unreliable, are denied or insecure (for example, in adefence context). These constraints often mandate the use of satellitecommunications. For example, for long range oceanic environmentalmonitoring for environmental, economic and national security reasons,satellite communications is the only feasible solution for command,control and extraction of sensor data. Often, this information will besensitive (for economic or national security reasons), and so a securecommunication system is required.

Unfortunately, existing commercial satellite services may be designedfor other applications. For example, at one end of the scale there areexpensive, real-time, broadband services. At the other end, there isone-way communications for very small amounts of data.

Prohibitive cost and technical constraints have limited widespread useof large numbers of remote field sensors. Accordingly, it appears thatremote communications are commonly under-utilised, or cumbersome datacollection is employed, for example, infrequent manual retrieval throughsite visits, diminishing the ability to collect critical data.

There is thus a need to provide a communications system and method whichprovides improved communication services for remotely deployedequipment.

SUMMARY

According to a first aspect of the present invention, there is provideda communication system, including:

-   -   a. a user node for receiving data from a remote application        program, the data including message data for communication to a        central application program operatively associated with the        remote application program;    -   b. a plurality of geographically distributed gateway nodes;    -   c. one or more access nodes for receiving the message data from        the user node via a first communications interface, and        communicating the message data via a second communications        interface to one or more of the plurality of geographically        distributed gateway nodes; and    -   d. a hub for communicating with the one or more of the plurality        of geographically distributed gateway nodes to receive the        message data for communication to the central application        program.

According to a second aspect of the present invention there is provideda communication system, including:

-   -   a. a central application program operatively associated with one        or more remote application programs;    -   b. a plurality of geographically distributed gateway nodes;    -   c. a hub for receiving data from the central application program        for communication to the one or more remote application programs        and communicating the received data to a selected one or more of        the plurality of geographically distributed gateway nodes; and    -   d. one or more access nodes for receiving the data from the        selected one or more of the geographically distributed gateway        nodes using a first communications interface, and communicating        the received data to the one or more remote application programs        using a second communications interface.

According to yet another aspect of the present invention there isprovided a communication system, including:

-   -   a. a first application program operating on or in connection        with a first communication node;    -   b. a plurality of geographically distributed gateway nodes;    -   c. a second application program providing data for communication        to the first communication node for processing by the first        application program; and    -   d. a central host for selecting one or more of the gateway nodes        for communicating the data to the first communication node for        processing by the first application program.

Another aspect of the present invention provides a method ofcommunication, including:

-   -   a. a user node receiving data from a remote application program,        the data including message data for communication to a central        application program operatively associated with the remote        application program;    -   b. one or more access nodes receiving the message data from the        user node via a first communications interface, and        communicating the message data via a second communications        interface to one or more of a plurality of geographically        distributed gateway nodes; and    -   c. a hub communicating with one or more of the plurality of        geographically distributed gateway nodes to receive the message        data for communication to the central application program.

Another aspect of the present invention provides a method ofcommunication, including:

-   -   a. operating a first application program on or in connection        with a first communication node;    -   b. providing a plurality of geographically distributed gateway        nodes;    -   c. operating a second application program providing data for        communication to the first communication node for processing by        the first application program; and    -   d. providing a central host for selecting one or more of the        gateway nodes for communicating the data to the first        communication node for processing by the first application        program.

Preferably, at least one of the access nodes includes a satellite basednode.

Preferably, the gateway nodes and/or the user node are low power nodes.In an embodiment, the low power nodes have an EIRP of less than 5 W.

Embodiments of the present invention may provide either one way(ground-to-satellite) or two-way (ground-to-satellite andsatellite-to-ground) communications.

It is envisaged that providing a geographically distributed set ofgateway nodes may increase the duration of connectivity between gatewaysand satellite payloads, and thus reduce data transfer latency.

Embodiments of the present invention are expected to provide advantagesin various application is requiring satellite based communicationssystems. By way of examples, such applications may include long rangeoceanic environmental monitoring, unattended ground sensors, andmonitoring and control of remote assets for the mining industry.

BRIEF DESCRIPTION OF DRAWINGS

A preferred embodiment of the present invention will be discussed withreference to the accompanying drawings wherein:

FIG. 1 is a data flow diagram showing a unidirectional message transferfrom one or more remote application programs to a single centralapplication;

FIG. 2 is a data flow diagram showing a bidirectional message transferbetween one or more remote application programs and a single centralapplication program;

FIG. 3 is a system block diagram for a communication system according toan embodiment of the present invention;

FIG. 4 is a functional block diagram for a node architecture suitablefor use with a communication system in accordance with an embodiment ofthe present invention;

FIG. 5 is a functional block diagram for a ST1 recorder node suitablefor use with a communication system in accordance with an embodiment ofthe present invention;

FIG. 6 is a block diagram for a system in accordance with an embodimentincluding a multimode gateway/access terminal operating in a access nodemode in accordance with an embodiment of the present invention;

FIG. 7 is a block diagram for a communication system in accordance withan embodiment including a multimode gateway/access terminal operating ina gateway mode in accordance with an embodiment of the presentinvention;

FIG. 8 is a block diagram for a system in accordance with an embodimentincluding a multimode gateway/access terminal simultaneously operatingin a gateway node and an access mode;

FIG. 9 is a block diagram for a system in accordance with an embodimentincluding plural multimode gateway/access terminals;

FIG. 10 is a functional block diagram for a central host suitable foruse with a system in accordance with an embodiment of the presentinvention;

FIG. 11 is a system block diagram for an example implementation of asystem in accordance with an embodiment of the present invention;

FIG. 12 is a protocol stack structure suitable for use with anembodiment of the present invention;

FIG. 13 depicts one embodiment of a compact antenna;

FIG. 14 depicts a further embodiment of a compact antenna; and

FIG. 15 depicts test results including SNR measurements.

In the following description, like reference characters designate likeor corresponding parts throughout the figures.

DESCRIPTION OF EMBODIMENTS

An embodiment of the present invention will now be described in terms ofa satellite communication system which provides services which allowmessage store and forward between remotely deployed equipment and acentralised control and management system of an end user via a satellitebased access node. In general terms, the types of services provided bythe system may include communication services, system services and userservices.

In terms of communication services, in the present example, two types ofcommunication services may be provided by an embodiment of thecommunication system, namely, Service Type 1 (hereinafter “ST1”) andService Type 2 (hereinafter “ST2”). Service Type 1 (ST1) is a 1-wayservice, catering to terminals with small transmission sizerequirements, whereas Service Type 2 (ST2) is a 2-way service, cateringto terminals with larger data transfer requirements. Both the ST1 andST2 service types may be provided within a common messagestore-and-forward network framework.

The service types provided by embodiments of the system may cater forunidirectional (that is, one way) communication or bidirectional (thatis, two-way) communication respectively In this respect, the describedembodiment of the present invention relates to an integratedcommunication service offering both service types. However, it is to beappreciated that it is not essential that all embodiments of the presentinvention offer both communication service types. In this respect, FIG.1 shows an example of a unidirectional message transfer from one or moreremote application programs 100 (shown as RA-1A, RA-2A, and RA-3A) to asingle central application program 102 (shown as CA-A) using aunidirectional service 104 (shown as ST-1). On the other hand, FIG. 2shows an example of a bidirectional message transfer between one or moreremote application programs 100 (shown as RA-1A, RA-2A, and RA-3A) and asingle central application program 102 (shown here as CA-A) using abi-directional service 200 (shown as ST-2).

FIG. 3 shows a block diagram for a communication system 300 inaccordance with an embodiment of the present invention. As shown, thesystem 300 includes plural remote application programs 100 (shown asRA-1A, RA-1B, RA-2X, and RA-3A), plural user nodes 304 (shown as UN-1,UN-2, UN-3), an access node 306 (shown as AN-1), geographicallydistributed gateway nodes 308 (shown as GN-1, GN-2), central applicationprograms 102 (shown as CA-A, CA-B, CA-X, CA-Y), access node applicationprogram (shown as ANA-1X), and a central application hub 312 (shown asCAH). It will of course be appreciated that the number of remoteapplication programs 100, central application programs 102, access nodes306, user nodes 304, and gateway nodes 308 included in the illustratedembodiment is not intended to limit the scope of the invention.Accordingly, other embodiments of the present invention may include adifferent number of remote application programs 100, central applicationprograms 102, user nodes 304, access nodes 306, gateway nodes 308, andpotentially central application hubs.

In the present case, each node is an individually addressable functionalnetwork entity that provides radio communication services within thesystem 300. Each user node 304 provides communication services to one ormore of the remote application programs RA-1A, RA-1B, RA-2X, and RA-3Awhich allows the remote application programs to communicate with anassociated central application program CA-A, CA-B, CA-X, CA-A via thecommunications system 300. Two logical communication interfaces are alsoshown, namely the remote radio interface 314 (RRI), and the gatewayradio interface 316 (GRI). The nodes and the communication interfaceswill be described in more detail later.

In the present case, each of the functional network entities has accessto a common timing reference (not shown), such as a common timingreference provided by a Global Positioning System (GPS). Alltransmissions in the system 300 are time-synchronised to this reference.For convenience we shall use the term “GPS” to denote the common timingreference. However it will be appreciated that other time (and position)determination systems may be used.

The remote application programs 100 may be installed on a user device(not shown) equipped with suitable processing and communicationsinfrastructure, such as a user terminal (UT) or another device which isconnected to a suitable user terminal via a communications interface.The user or other device will typically be located in geographiclocations which are remote from its associated central applicationprogram and thus may be located in a region not readily accessible to auser.

The remote application program 100 may include, for example, anenvironmental monitoring remote application program for collecting,processing and transmitting environmental monitoring data (such astemperature, audio, video, and/or other sensor data) from one or moresensors; an asset monitoring remote application program for collecting,processing and transmitting of system monitoring data, such as frommining equipment, water infrastructure, energy infrastructure, transportassets and infrastructure; a remote application program for processingand/or forwarding of data within a SCADA system; a remote applicationprogram for monitoring and controlling local equipment in response tooperational commands issued by a corresponding central application; aremote application program for object position reporting, enablingobject tracking and monitoring services (objects may be land, air or seabased, and could be mobile or stationary); or a remote applicationprogram for delivering system services applications such as filetransfer, firmware upgrade (user terminal and/or application), and nodemonitoring and management.

In the present case, each of the plural remote application programs 100are operatively associated with a respective one or more of the centralapplication programs 102. In the system 300 illustrated in FIG. 3, theremote application programs RA-1A, RA-1B are operatively associated withcentral application programs CA-A and CA-B respectively, whereas remoteapplication programs RA-2X, and RA-3A are associated with centralapplication programs CA-X and CA-A respectively. In this respect,throughout this specification references to “operatively associated”,where used to describe a relationship between a remote applicationprogram and a central application program, are to be understood todenote a relationship in which the remote application program and thecentral application program are elements of a distributed application,and thus have a functional interdependency. In other words, the remoteapplication program and the central application operate in combinationto deliver or provide a service.

In embodiments of the present invention, a distributed application maybe formed through distribution of application programs (that is,software) running on multiple nodes of the system 300. In this respect,the term “software,” as used herein, includes but is not limited to oneor more computer readable and/or executable instructions that cause acomputer or other electronic device to perform functions, actions,and/or behave in a desired manner. The instructions may be embodied invarious forms such as routines, algorithms, modules or programsincluding separate applications or code from dynamically linkedlibraries. Software may also be implemented in various forms such as astand-alone program, a function call, a servlet, an applet, instructionsstored in a memory, part of an operating system or other type ofexecutable instructions. It will be appreciated by one of ordinaryskilled in the art that the form of software is dependent on, forexample, requirements of a desired application, the environment it runson, and/or the desires of a designer/programmer or the like.

Furthermore, those of skill in the art would appreciate that the variousillustrative logical blocks, modules, circuits, and algorithm stepsdescribed in connection with the embodiments disclosed herein may beimplemented as electronic hardware, computer software, or combinationsof both. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, circuits,and steps will be described in terms of their functionality. Whethersuch functionality is implemented as hardware or software depends uponthe particular application and design constraints imposed on the overallsystem. Skilled artisans may implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the present invention.

Preferably, distributed elements (that is, the application programs) ofthe distributed application can thus run in connection with any one ofany node(s) of the system 300. In this way, for example, an applicationprogram operatively associated with a central application program mayinteroperate to permit, for example, an increased level of access toservices, node system function access, firmware upgrade and remotemanagement. Interoperation of this type may also support collationand/or processing of message data, decision making, and possibly providea reduced load on communications interfaces.

In the example that follows, application programs will be described interms of the remote application programs 100 and the central applicationprogram(s) 102. However, it is to be appreciated that other applicationprograms may also be provided, such as, access node applications andgateway node applications, each of which may also be operativelyassociated with a central application program 102.

Each of the central application programs 102 may include an applicationprogram in the form of computer executable software installed on a userdevice such as a host computer accessible to a user and equipped withsuitable processing and communications infrastructure. Suitable hostcomputers may include a tablet, a desktop computer, a smart phone, alaptop computer, a notebook computer or the like.

One or more of the central application programs 102 may provide one ormore functions for controlling, managing, monitoring, configuring, orupdating the associated remote application program. Examples of centralapplication programs include an environmental monitoring centralapplication program for collating and/or processing sensor data from oneor more remote application programs and potentially combining geographicand sensor data to produce measures of distributed natural processes; anasset monitoring and tracking central application program for processingposition and sensor data from user assets and potentially providinghistorical, current and potentially estimated future locationinformation; a central application program for monitoring the state ofremote plant, and potentially processing state data to make decisionsabout future plant operations; a central application program fordistributing firmware upgrade data and commands to one or more remotenodes (which may include system and/or remote application programfirmware); a central application program for transmitting and receivingfiles to/from other nodes within the communication system 300.

In some embodiments, a central application program permits remotemanagement and control of the associated remote application program.Such a central application program may also send commands to amonitoring and control remote application in order to control, forexample, plant operation, and/or the collection of monitoring data to,for example, control and monitoring of a fleet of autonomous vehicles.

To access the services of the system 300, each of the centralapplication programs 102 is preferably required to register with thecentral application hub 312 (hereinafter the “hub”) by a suitableregistration process. Registration of each of the central applicationprograms 102 with the hub 312 may be performed, for example, across anetwork for example, via an Internet Protocol based mechanism.Similarly, each of the remote application programs 100 are preferablyrequired to register with a respective one of the user nodes 304 via asuitable registration process using a suitable application interfacesuch as an application interface protocol operating over IP services(for example, TCP), or a software API employing software function calls.

Once registered, a remote application may transmit messages to itsassociated central application program via the user node with which ithas registered.

In the embodiment illustrated in FIG. 3, one or more of the user nodes304 may provide a message storage function (MSF) which:

-   -   Stores partial messages received from the access node 306, until        all message fragments are received. When a message is fully        received, it is delivered to a destination remote application        program; and    -   Stores messages from a remote application RA-1A, RA-2A, RA-2X,        and RA-3A connected to a user node UN-1, UN-2, UN-3 until the        access node 306 becomes available to allow outgoing messages to        be transmitted.

One or more of the user nodes 304 may also provide system managementservices, such as:

-   -   A firmware upgrade mechanism to allow all aspects of the node        software/firmware to be reliably upgraded; and    -   Node management services.

In some embodiments, the user nodes 304 may compress data prior totransmission to reduce load on the communications interfaces 314, 316.

Gateway Nodes

In the embodiment depicted in FIG. 3, each of the plurality of gatewaynodes 308 are geographically distributed over an area and providecommunication services to the hub 312 and the access node 306 forcommunicating messages to/from the central application programs 102.Each gateway node GN-1, GN-2 also provides the gateway radio interface316 and an application interface as described below.

The gateway nodes 308 also provide a connection to the hub 312, theavailability of which may be:

-   -   Persistent: for example, via a permanent Internet connection; or    -   Intermittent—for example, via a wireless network connection that        becomes active when a mobile Gateway Node moves into range of        the network.

Each of the plurality of gateway nodes 308 may provide a message storagefunction (MSF) at the gateway which:

-   -   Routes messages between the hub 312 and the one or more access        nodes in the system 300.    -   Stores partial messages received from the access node 306, until        all message fragments are received. Messages (or received        message fragments in the case of a broken connection) are        delivered to the hub 312 for delivery to its destination central        application program CA-A, CA-B, CA-X, CA-Y. In the case of a        broken connection, remaining fragments at the access node 306        may be delivered to a different gateway node for message        re-construction at the hub 312. If a connection to the hub 312        is not available, the message is stored until a connection        becomes available.    -   Stores messages destined for a remote application RA-1A, RA-1B,        RA-2X, RA-3A received from the hub 312 until the access node 306        becomes available to allow outgoing messages to be transmitted.    -   Stores messages received from local gateway node applications        (via an application interface) until a connection to the        destination becomes available, for example, via the access node        306 or hub 312 connection.

Each gateway node GN-1, GN-2 may also provide system services, such as:

-   -   A firmware upgrade mechanism to allow all aspects of        software/firmware installed on the gateway node to be reliably        upgraded; and    -   Node management services described below.

In some embodiments, one or more of the gateway nodes 308 may beinstantiated as a special type of user node, which is given priorityaccess to the radio interface. Furthermore, one or more of the gatewaynodes 308 may compress data prior to transmission to reduce load on theradio interface.

One or more of the gateway node 308 may be located on the surface of theearth, be airborne, or space-based.

Access Nodes

The access node 306 may include a space-based, airborne, or terrestrialentity providing:

-   -   1 and/or 2-way communication with remote terminals via the        remote radio interface 314;    -   1 and/or 2-way communication with gateway terminals via the        gateway radio interface 316; and    -   An application interface.

In the embodiment illustrated in FIG. 3, the access node 306communicates message data intended for communication to one or more ofthe central applications programs 102 via a selected one of the gatewaynodes 308 and the hub 312. However, it is also possible that the accessnode 306 may communicate directly with the hub 312. The access node 306to hub 312 connection may be:

-   -   Persistent—for example, via a permanent Internet connection; or    -   Intermittent—for example, via a wireless network connection that        becomes active when a mobile Access Node moves into range of the        network.

Preferably, the access node 306 also provides a message storage function(MSF) which:

-   -   Stores messages received from user nodes 304 for communication        to one or more of the central application programs 102 from one        or more remote applications 100 connected to a respective user        node UN-1, UN-2, or UN-3;    -   Stores messages received from one of the plurality of gateway        nodes 308 for communication to one or more of the user nodes        304; and    -   Stores messages received from local access node applications        (shown as ANA-1X) until a connection to the destination becomes        available, for example, via a gateway node 308 or hub 312        connection.

The access node 306 may also provide system management services, suchas:

-   -   A firmware upgrade mechanism to allow all aspects of        software/firmware installed on the access node 306 to be        reliably upgraded; and    -   Node management services described below.

The access node 306 may also provide one or more of the followingservices:

-   -   Real-time message forwarding between the central applications        programs 102 and their respective associated remote application        program RA-1A, RA-1B, RA-2X, or RA-3A when the access node 306        has simultaneous connections to one or more of the user nodes        304 and to the hub 312 (either directly or via the system, for        example, through one of the plurality of gateway nodes 308).    -   Real-time message forwarding between remote application programs        100 that are connected to a respective one of the user nodes 304        when the access node 306 has a simultaneous connection to the        respective user node UN-1 or UN-2.

Preferably, the access node 306 controls network access rights for thesystem entities, such as the user nodes 304 and the gateway nodes 308.Control of this type may be applied to attributes such as:

-   -   Maximum data transfer size; and    -   Priority of message delivery.

In this respect, rights may be controlled taking into account systemattributes, such as:

-   -   An identifier assigned to the user and/or gateway nodes or a        group of user nodes and/or gateway nodes;    -   The geographic location of the user and/or gateway nodes; and    -   Current time.

The access node 306 may receive centralised network access controlinstructions setting the network access rights from the hub 312. It ispossible that the access node 306 may compress data prior totransmission, thus reducing load on the communications interfaces 316(GM) and/or 314 (RRI).

The gateway radio interface 316 may be implemented as a 1-waycommunication from the access node 306 to the plurality of gateway nodes308. In such an implementation, the access node 306 may use a ratelesscoding scheme (for example, Fountain codes or Raptor codes) to transmitcoded packets to the plurality of gateway nodes 308. The gateway nodes308 will then forward the received packets to the hub 312 where theywill be decoded.

Service Type 1 Recorder Node (St1RN)

Embodiments of the present invention may include an ST1 Recorder Node(ST1RN) which provides the following for Service Type-1:

-   -   Support for embodiments in which the ST1 receiver signal        processing is performed on samples recorded by the node,        potentially at a location away from the node;    -   Reception and recording of ST1 signals from the remote radio        interface 314;    -   1 and/or 2-way communication with gateway terminals via the        gateway radio interface 316.

Recorded channel data may be forwarded over the gateway radio interface316 for signal processing away from the node, for example, from asatellite to a central ground station, or from a terrestrial node to acentral processing location; and

-   -   Time and (potentially node position) stamping of recorded        samples.

The ST1RN may also provide an application interface for access to systemmanagement services, such as:

-   -   A firmware upgrade mechanism to allow aspects of the node        software/firmware to be reliably upgraded; and    -   Node management services described below.

The ST1RN may compress recorded channel data prior to transmission, thusreducing load on the communications interface. The ST1RN may include aspace-based, airborne, or terrestrial entity

Central Application Hub (CAH)

The central application hub 312 provides communication services for thecentral applications programs 102. The hub 312 allows the centralapplication programs 102 to register, and provides an applicationinterface by which the central application programs 102 may communicatewith their associated remote application RA-1A, RA-1B, RA-2X, or RA-3A.In this respect, in the system 300 illustrated in FIG. 3:

-   -   CA-A is associated with to RA-1A, RA-3A (for example, position        tracking service);    -   CA-B is associated with RA-1B (for example, sensor network        service);    -   CA-X is associated with ANA-1X and RA-2X. In this distributed        case it may be that a service has CA-X communicating with ANA-1X        and RA-2X individually, for example, a system service that        gathers node statistics. Alternatively it may be that CA-X        communicates with ANA-1X (for example, to upload a file) and        then later ANA-1X communicates with RX-2X to allow it to        download that file, for example, in a file transfer service; and    -   CA-Y is associated with GNA-1Y (for example, system service for        gateway management).

The hub 312 may route messages to/from the access node 306 eitherdirectly, or via one or more of the plurality of gateway nodes 308.

As shown in FIG. 3, in an embodiment an interface is provided betweenthe central application programs 102 and the hub 312. This interface maybe provided using the Internet Protocol (IP). The interface may providethe following functions:

-   -   Application registration mechanism, which allows for central        applications to register for messaging services; and    -   Message a transportation mechanism (for example, via IP, UDP or        TCP).

The hub 312 may also provide the message storage function (MSF) whichperforms:

-   -   Node routing; and    -   Central application routing.

Further explanation of the message storing function of the hub 312 isset out below.

Node Routing

In an embodiment, the hub 312 may perform node routing of message datadepending on the availability for communication of the access node 306or the plurality of the gateway nodes 308. For example, if the hub 312has an active direct connection to the access node 306 (in other words,a connection which does not require a gateway node 308, the hub 312 mayroute messages directly to the access node 306. Alternatively, the hub312 may route messages for communication to the access node 306, or forcommunication to a user node UN-1, UN-2, UN-3, through the access node306, via one of the plurality of gateway nodes GN-1, GN-2.

In some embodiments, the hub 312 may receive reports of partialtransmission from a gateway node GN-1, GN-2 or the access node 306.Based on a received report, the hub 312 may then re-allocate thetransmission of remaining message fragments which may potentiallyinvolve a different gateway node or access node.

Central Application Routing

The hub 312 may perform node routing of message data which involvesrouting all messages from user nodes 304 to an addressed centralapplication program 102. In the event that an addressed centralapplication program 102 is not available for communication with the hub312, the hub 312 may store messages for communication to that centralapplication program at a later time.

It is preferable that the hub 312 selects a message route which reducesmessage delivery latency. For example, when routing a message to theaccess node 306 via one of the plurality of gateway nodes 308, the hub312 may use (expected or actual) geographic information relating to thegateway nodes GN-1, GN-2 and/or access nodes in order to select thegateway node GN-1, GN-2 that is expected to be within range of theaccess node 306 in the nearest time. It is possible that a similarapproach may be used to geographically route messages to user nodes 304via a selected access node.

For the purposes of geographic routing and broadcast or multicastmessage transmission, geographic “transmission regions” may be definedso that transmission regions may be specified for individual messages.Methods for defining such transmission regions may include:

-   -   Boundaries specified in terms of latitude and longitude limits,        for example, defining regions using an upper and lower corner        boundary specification;    -   Using international country codes, allowing specification by        country rather than geographic boundaries; and    -   Pre-defining a list of regions with a region index being        assigned to each region.

In some embodiments; the hub 312 may select a transmission region tobalance load across the system 300, for example, avoiding routes througha heavily loaded gateway node when an alternate route is available.

It is preferred that the hub 312 maintains connectivity with gatewaynodes 308, and provides centralised control and monitoring of each ofthe plurality of gateway nodes 308.

In some embodiments, the hub 312 also provides system services, such as:

-   -   Distribution of firmware/software upgrades to nodes within the        system 300; and    -   Centralised server component of the remote management service        described below.

It is notable that although the embodiment illustrated in FIG. 3includes a single hub 312, it is possible that the other embodiments ofthe system 300 will provide multiple central application programconnection points through multiple hubs. In such embodiments, each ofthe plurality of gateway nodes 308 may be tasked to route to a differenthub 312 based on identification of the central application. In oneembodiment, one or more central application hubs may be dedicated tosystem services. In another embodiment one or more central applicationhubs may be limited such that they can only provide access to userservices.

Node Management

As briefly explained above, each node (that is, each user node, accessnode and gateway node) of the system 300 may provide node managementfunctions which are adapted to provide a common and consistent interfaceto each of the subsystems operating on a node, and which may providemechanisms to:

-   -   Obtain information about the state of node subsystems, for        example, event counters and flags;    -   Provide configuration data to node subsystems; and    -   Provide control of node subsystems.

In some embodiments, remote access to node management may be providedvia a remote management service described later.

Time And Positioning Services

In the embodiment of the system 300 depicted in FIG. 3, the user nodes304, access node 306, and the plurality of gateway nodes 308 have accessto a common timing reference through an input interface for timingsynchronisation.

It is also possible that the user nodes 304, access node 306, and theplurality gateway nodes 308 also have access to a source of positioninformation which provides position information to node functions.

The timing reference and position information services may also beprovided externally to applications registered with the node.

Entity Interfaces

As shown in FIG. 3, the system 300 provides interfaces for providingand/or managing the communication of the message data across the system.These interfaces include:

-   -   Radio interfaces 314, 316; and    -   Application interface (not shown).

The role of the radio interfaces 314, 316 and the application interfaceis described below.

Radio Interface

The radio interfaces 314 (RRI), 316 (GRI) provide a shared physicalcommunications medium which may be partitioned into a number ofchannels. These channels may be time slots in a time division multipleaccess system, frequency slots in a frequency division multiple accesssystem, subcarriers in an orthogonal frequency division multiple accesssystem, or spreading sequences in a code division multiple accesssystem. More generally, the slots may be hybrids of any of these, wherea slot corresponds to some subset of the overall degrees of freedom ofthe system (including degrees of freedom resulting from the use ofmultiple transmit and or receive antennas). Regardless of the underlyingmethod of dividing the medium into channels, we shall refer to thesechannels as “slots”. We do not require that the slots be orthogonal,although in many instances slots are chosen to be orthogonal.

For the purpose of this description, a grouping of a whole number ofslots shall be referred to as a “frame”. In the present case, framedimensioning in the system 300 is determined by the access node 306. Theaccess node 306 preferably also controls the ratio of slots allocated toaccess node transmit and receive directions within each frame.

Timing is synchronised throughout the system 300 via the common timingreference described previously.

The radio interfaces 314 (RRI), 316 (GRI) may employ multiple radiochannels, providing increased bandwidth to service gateway and usernodes. The ability to add further channels (and potentially do sopost-deployment) provides a scalable radio interface. The system 300 maythus adapt its use of channels during operation, for example, to providea dedicated set of channels for gateway communication, or to cater fordifferent channel allocations on a regional basis.

As explained previously, the Service Type-2 (ST2) radio interfaceprovides a bi-directional remote radio interface (RRI) between theaccess node 306 and the user nodes 304. It may also be used, to providea bi-directional gateway radio interface 316 (GRI) between the accessnode 306 and one or more of the plurality of gateway nodes 308.Reception of data from a user node UN-1, UN-2, or UN-3 or a gateway nodeGN-1 or GN-2 may be acknowledged by the access node 306, and vice versa.

ST2 medium access arbitration is preferably coordinated by the accessnode 306. During this process the access node 306 preferably performsthe following functions:

-   -   1. Allocates transmission slots within frames to user nodes,        gateway nodes and access node based on:        -   Requests for access from user nodes and gateway nodes;        -   Messages stored in the access node message storage function;            and        -   The detected presence of user nodes and gateway nodes within            the current access node range.    -   2. Allocates packets for transmission to access node        transmission slots; and    -   3. Regularly transmits announcement messages, announcing the        presence of access node and ST2 communication services.

During ST2 medium access arbitration a user node or gateway nodepreferably performs the following:

-   -   1. Listens for access node announcement messages;    -   2. Announces its presence to new access nodes, and requests        access to ST2 channel resources if it has data to transmit; and    -   3. Notifies higher layer services when the channel state changes        (active/inactive).

The access node announcement may also include the position of the accessnode. The user node or gateway node may use this information to improveradio link quality, for example, by steering a directional antennatoward the access node.

The remote radio interface 314 (RRI) and the gateway radio interface 316(GM) will now be described in more detail.

Remote Radio Interface (RRI)

In the embodiment illustrated in FIG. 3, the remote radio interface 314(RRI) provides a primary communications interface between the remotelylocated user nodes 304 and the access node 306. The remote radiointerface 314 (RRI) may provide multiple different radio interfaces(Physical and Link Layer) to handle differing types of userapplications.

As previously described, the Service Type-1 (ST1) radio interface is aunidirectional interface providing message transfer in the directionfrom user node 304 to access node 306 only. It is notable that the ST1radio interface may also include a transfer mechanism in the access nodeto user node direction that is available for purposes other than messagetransfer.

Reception of data from a user node 304 may be acknowledged by the accessnode 306 using a suitable acknowledgement process.

Transmissions from the access node 306 may also be used by the usernode(s) 304 for one or more of the following:

-   -   detecting the presence of the access node 306;    -   aligning user node(s) 304 transmissions in time and/or        frequency, using the access node 306 as a reference; and    -   coordinating user node(s) 304 slot access.

The case when the ST1 radio interface operates without an access node306 to user node 304, a feedback channel allows for transmit-onlyimplementation of the user node. In the absence of a feedback channel,slot access may be coordinated.

ST1 user nodes may use position and knowledge of time of day, togetherwith pre-programmed knowledge of access node behaviour (for example,orbit parameters in the case of a satellite system) to decide when totransmit. Furthermore, repeated transmission by a ST1 user node may beused to implement a degree of priority or Quality of Service (QoS),where repeat rate may be changed in order to change priority.

Turning now to the Service Type-2 (ST2) radio interface, the ST2interface provides a bi-directional remote radio interface between theaccess node 306 and the user nodes 304, as described above.

User services will either use the ST1 or ST2 based services, dependingupon the user application requirements. Application access to both ST1and ST2 services may be provided by a common messaging interface.

Gateway Radio Interface (GRI)

In embodiments, the gateway radio interface 316 (GRI) provides aunidirectional or bi-directional communication link between the accessnode 306 and a gateway node 308 over which:

-   -   Messages from user nodes 304 (or from access node applications        ANA-1X) may be transferred to the hub 312; and    -   Messages from the hub 312 may be transferred to the access node        306, to an access node application, or for communication to a        user node UN-1, UN-2.

The specification and implementation of the gateway radio interface 316(GRI) may be based upon the data throughput requirements of the system300.

The gateway radio interface 316 may be implemented using thebi-directional Service Type-2 (ST2) radio interface described above, orin the case of a satellite mounted access node, via an existing TT&Clink to the spacecraft or the Consultative Committee for Space DataSystems (CCSDS) File Delivery Protocol, or via some other suitablecommunications mechanism which provides sufficient resources totransport data between the gateway node and the access node, forexample, a C-band or S-band link.

Application Interface

The application interface provides the applications programs with apoint of access to communications and system management servicesprovided by the system 300.

In embodiments, the application interface provides a mechanism by whichthe remote and central application programs, and possibly access nodeapplication programs and /or gateway node application programs ifprovided, register with the communications system 300, in order to useservices. Registration informs functional entities that the applicationis present and may therefore accept delivery of messages. Theapplication interface may also provide a mechanism through which themessages may be transported to/from the applications.

Examples of the application of an application interface include:

-   -   Remote applications 100 may use the application interface        provided by their respective user nodes 304 hosting or in        communication with the remote application;    -   Access node applications (for example, ANA-1X) may use the        application interface provided by the respective access node        (for example, AN-1) hosting or in communication with the access        node application;    -   Gateway node applications may use the application interface        provided by the gateway node hosting or in communication with        the gateway node applications; and    -   Central applications may use the application interface provided        by the hub 312.

In addition to the functionality provided for user services, systemservices may be given access to system functions such as those providedfor node management.

Application Programs

Application programs may be either system level or user applicationprograms which utilise the system or user services. Such system or userservices may utilise the communication system services. In someembodiments, an application program may be implemented on the samedevice as the functional network entity, or on a different physicaldevice to which it has a connection. This connection may be provided viasome network, such as a wired or wireless local area connection, or viathe internet. It is preferred that application programs be controlledand/or re-programmed via the communications system 300.

Remote Application Programs (RA)

Each remote application program registers with a respective user node304, and may communicate with its associated central application program102 via the communication services of the user node UN-1, UN-2, or UN-3with which it has registered. Once so registered, the remote application100 accesses services provided by the user node UN-1, UN-2, or UN-3, viauser node's application interface.

By way of an example, a remote application may include a remote sensingapplication that performs the following functions:

-   -   Measures environmental parameters, for example, temperature, and        sends this information along with the user node position and        time, to its corresponding central application; and    -   Receives control information from its corresponding central        application, for example, to change the time of day at which        measurements are recorded.

Note that the first function, that is, the measurement of environmentalparameters, may be provided via the ST1 and ST2 services. On the otherhand, the second function, that is, receiving control information,requires message delivery from central application to the remoteapplication and thus the bidirectional ST2 service.

Central Application Programs

Each central application program 102 may communicate with one or more ofthe remote application programs 100, the access node 306, or one or moreof the plurality of gateway nodes 308 by sending and receiving messagesvia the hub 312 using services provided by the hub 312 via itsapplication interface.

In terms of an example central application program corresponding to theexample remote sensing remote application program described above, thecentral application program may:

-   -   Collate and process messages received from the remote        application and then deliver a summary to users;    -   Allow end users to send commands to control the operation of the        remote application.

Access And Gateway Node Application Programs

In some embodiments, access node application programs (for example,ANA-1X) and gateway node application programs (for example, GNA-1Y) areprovided. These application programs may offer the potential forprovision of additional services beyond message store-and-forward, byallowing on-board data processing and decision making at these gatewayand access nodes respectively. These application programs may accessservices via the respective application interface.

An access node application program may provide a file transfer servicethat:

-   -   Allows a file to be received from the hub 312 and stored at the        access node 306, potentially across several time separated        connections;    -   Manages the distribution of the file to one user node UN-1,        UN-2, or UN-3 (via unicast) or several user nodes (via multicast        or broadcast); and    -   Deletes the file at the access node upon receiving verification        from the recipient user node that the file was received intact.

System Application Programs

The concept of central and remote application programs also extends tothe operation of the system 300. For example, some higher-level servicesprovided by the system 300 may be provided by system applicationprograms which operate on the nodes of the system. These system servicesmay include, for example:

-   -   Firmware upgrade service (FWUS); and    -   Remote management service (RMS).

In some circumstances, a system application program may be givenpriority over user applications when accessing the communications system300. Further explanation of the firmware upgrade service and the remotemanagement service is set out below.

Firmware Upgrade Service

The Firmware Upgrade Service may provide a mechanism by which firmwareoperating on system nodes (304, 306, 308) or devices connected to thesenodes may be upgraded in the field via the service. The service mayprovide a mechanism for:

-   -   Transmitting firmware upgrade data to target node(s), either        using broadcast, multicast or unicast transmissions;    -   Coordinated control and scheduling of the deployment of firmware        upgrades;    -   A file transfer service (FTS), as described above.

The firmware upgrade service may be implemented with a central firmwareupgrade server application responsible for disseminating firmwareupgrade data to remote system nodes. A corresponding client applicationat the nodes receives firmware data and command/control data.

Remote Management Service

The remote management service may allow for the remote control andmonitoring of nodes within the system 300, providing remote access tonode management functionality. Is it possible that a central monitor andcontrol server application, connected to the system 300 via the hub 312,may examine the status of system nodes, and send configuration and/orcontrol data to system nodes. In this respect, each node may run aclient application which is responsible for executing status orconfiguration change requests received.

Authentication And Security Services

It is preferred that the system nodes (that is, the user nodes, accessnodes and gateway nodes) include an authentication and securitymechanism to employ security mechanism at several levels within thesystem 300.

For example, embodiments of the present invention may provide anauthentication mechanism to verify the identity of nodes within thesystem. In some embodiments, an authentication mechanism is used toensure that, firstly, at a link level, only authorised nodes (inparticular user nodes and gateway nodes) may obtain access to the remoteradio interface 314 (RRI) and/or the gateway radio interface 316 and,secondly, at a service level, that the authenticity of a message can beverified (a guarantee that the message originated at the stated sourcenode, and was not tampered within transit).

In some embodiments, an encryption mechanism may be provided to ensureprivacy of communications. For example, at a link level this wouldprovide privacy over the air-interface (that is, the RRI or GRI) betweennodes, or at the service level, this would provide privacy of end-to-endmessage communication, between RAs and CAs.

Link Authentication Services

Link-level authentication may employ a public key authentication schemeto provide an assurance to both communicating nodes that each is trustedby the system central Certificate Authority. Signed public keys would beexchanged in the RRI and/or GM channel access mechanism, allowing eithernode to generate signatures during the link communication session.

Link Encryption Services

Link-level encryption may be achieved by several means. Two optionsinclude:

-   -   Use asymmetric public/private key encryption mechanisms; and    -   Use a symmetric cypher with an appropriately generated session        key shared via a secure mechanism between the two nodes at        session establishment.

Message Authentication Services

Systems according to embodiments of the present invention may providefor authentication of messages within the system 300. Suchauthentication may be achieved using, for example, an algorithm whichgenerates a Message Authentication Code, which employs either anappropriately derived shared-secret between the message-originating nodeand destination central application, or a set of public and private keys(asymmetric digital signature scheme).

Authentication systems often require unique nonce values to begenerated. Nonce values-may be generated using the system time, which isguaranteed to produce a stream of unique values. Duplicate nonces may beavoided by limiting the rate at which messages are generated, so thatall messages have a unique time-stamp. Alternatively a mechanism toextend nonces for messages generated with the same time-stamp may beemployed.

Messages transported using ST1 or ST2 services may use the sameauthentication mechanism, providing interoperability between the twoservices.

Key Management Services

In some embodiments, a public key signature system is used to provide aprimary means of authentication within the system 300. In such a case,all nodes and central applications shall be assigned unique public andprivate key pairs.

A system wide trusted Certificate Authority may issue and sign keys,allowing for efficient key verification by nodes that deal with largenumbers of node interactions (for example, ANs communicating with alarge population of UNs), without requiring the distribution of largenumbers of keys within the system.

Protocol Stack

Turning now to FIG. 12, there is shown a protocol stack structuresuitable for use with an embodiment of the present invention. As shown,in a preferred embodiment, communication system functionality isdistributed across a protocol stack 1200. As is shown in in FIG. 12, theprotocol stack 1200 includes plural protocol layers, namely, a PhysicalLayer (PITY) 1202, a Medium Access Control layer (MAC) 1204, a MessageNetworking Layer (MNL) 1206 and an Application Layer 1208.

The Physical layer (PHY) 1202 determines how bits are physicallytransmitted on a radio channel. This includes determining, for example,bit ordering, modulation, channel coding, synchronisation and detectionmechanisms.

The Medium Access Control layer (MAC) 1204, also referred to as the LinkLayer, determines how access to the radio channel is organised andcontrolled. This includes, for example, protocols for error detectionand data re-transmission, session establishment and channel organisationand sharing amongst multiple users.

The Message Networking Layer (MNL) 1206 determines how data istransported between different logical entities in order to provideend-to-end communication service between remote and central applicationsin the system.

The Application Layer 1204 provides an application interface throughwhich application programs may access communications and systemmanagement services.

The Physical Layer (PHY) 1202, Medium Access Control layer (MAC) 1204,Message Networking Layer (MNL) 1206 and Application Layer 1206 will nowbe described in more detail.

Physical Layer (PHY)

The Physical Layer (PHY) 1202. implements the physical communicationslink between user nodes 304 and the access node 306 (a component of theRRI), and between gateway nodes 308 and the access node 306 (a componentof the GRI). This implements the ST1 and ST2 service waveforms. In thepreferred embodiment all communication in the system is packet based.

PHY Elements

The PPDU (PHY Protocol Delivery Unit) is the structure of the PHYpacket, as it is transmitted on the radio interface. It includesnotional guard periods, synchronisation and training sequences, FECencoding and data symbols.

The PSDU (PHY Service Delivery Unit) is the user data portion of thePPDU. This is the higher-layer protocol data that is transported withinthe PPDU packet. The PSDU contains the. Medium Access Control Layerpacket (or MPDU, Medium Access Control layer Protocol Delivery Unit).

ST1-PHY

The ST1-PHY provides a unidirectional transmission service. In anembodiment, all PPDU packets are transmitted time-synchronised to GPStime (see Medium Access Control Layer below).

In an embodiment, the ST1-PHY provides the following functions:

-   -   PSDU transmit (for user nodes);    -   Multi-user PSDU receiver (either implemented in the AN, or as an        offline service, for example, using samples recorded by the        ST1RN);    -   Measurement and reporting of channel parameters to upper        management layers (for example, MAC Management), including:        -   Number of users detected; and        -   Per-user channel parameters such as timing offset, frequency            offset, rate of change of frequency offset, and SNR.

A suitable ST1 Physical Layer is described in Australian PatentApplication No 201303163, the entire contents of which are hereinincorporated by this reference.

ST2-PHY

The ST2-PHY provides a 2-way communication service between usernodes/gateway nodes and access nodes. In an embodiment, two ST2-PHYsignal and packet types are employed, one for the downlink signal,ST2-DN, and one for the uplink, ST2-UP. The ST2-UP uplink and the ST2-DNdownlink may operate on the same channel or on different channels. Thesystem may also operate in a time-division duplex (TDD) orfrequency-division duplex (FDD) manner.

In an embodiment, all transmissions are time-synchronised with GPS time.

Access to a channel may be coordinated by the access node, andfrequency-synchronised to the access node's carrier frequency. TheST2-UP and ST2-DN signalling schemes operate together in order tosynchronise ST2-UP transmissions with an ST2-UP receiver, which may belocated, for example, in a satellite.

Alternatively, the system nodes may use an alternate access mechanism tocommunicate directly in the absence of coordination from an access node.For example, user (or gateway) nodes may access a channel using methodsknown to those skilled in the art, such as carrier sense multiple access(CSMA), or self organising time division multiple access (SOTDMA). Suchnodes may also continue to sense for the presence of an access node.Upon detecting transmissions from an access node the nodes then switchtheir operation such that their channel access is access nodecoordinated. Once the access node is no longer detected the nodes mayrevert to their alternate access mechanism.

The ST2-PHY may provide the following functions, for both the ST2-UP andST2-DN signalling schemes:

-   -   PSDU transmit and receive; and    -   Measurement and reporting of channel parameters to upper        management layers (for example, MAC Management) such as timing        offset, frequency offset, rate of change of frequency offset,        and SNR.

Medium Access Control Layer

In an embodiment, the Medium Access Control Layer (MAC) 1204 providesmechanisms by which access to the shared radio resource may be managedbetween the system nodes, and a means to transmit data between nodeswithin the system from user nodes/gateway nodes to access nodes, andvice-versa.

The MAC may provide the following functionality:

-   -   A common addressing scheme to uniquely identify nodes within the        system;    -   Packet transfer services between user nodes/gate way nodes to        access nodes;    -   Coordination of use of one or more radio channels by the system,        including:        -   a. Frame timing reference;        -   b. Frame timing and access rules enforcement;        -   c. Time Division Multiplexing allocation and management; and        -   d. Multiple channel operation management.

Data Services

The MAC may provide the following data services:

-   -   ST1 unacknowledged small message service (UMS) and acknowledged        small message service (AMS), as follows:        -   a. For small payload transmissions, for example, containing            position and sensor data;        -   b. Transmitted using the ST1 access mechanism; and        -   c. Maximum size limited by the ST1-PHY PSDU transmission            size.    -   ST2 unacknowledged message service (UMS)        -   a. Transmission of small to large payloads without            confirmation of delivery.    -   ST2 acknowledged message service (AMS)        -   a. Transmission of small to large payloads.        -   b. Transmission of messages where notification of delivery            is important.        -   c. Provides acknowledgement response to higher layer.    -   Protocol multiplexing, allowing multiple protocols to operate        over the service.

Medium Access

The Medium Access Control scheme may include a slotted, semi-scheduledTDMA scheme. All nodes in the system are preferably time-synchronisedvia the GPS system.

The MAC layer may be position aware, and thus able to use user nodeand/or access node position data to aid resource allocation decisions,using techniques such as those described in described in InternationalPatent Application No PCT/AU2013/000895.

In one embodiment, the system employs the following radio channelresources:

-   -   RC1 (Radio Channel 1). A radio channel which is used for ST1        burst transmissions from user nodes.        -   a. Uncoordinated Time and Frequency, Slotted-ALOHA with            multi-user detection.    -   RC2 (Radio Channel 2). A radio channel which is used for ST2        communications between user nodes/gateway nodes and an access        node.    -   a. Centrally coordinated slotted-TDMA. The radio channel is        shared between the access node and user nodes/gateway nodes in a        time/frequency-division multiple-access manner, under control of        the access node.

Another embodiment of the system may be extended to support operation onmultiple additional radio channels, subject to access nodes and usernode/gateway node radio capabilities, and the regulatory environment.

In a preferred embodiment, all transmissions of ST1 and ST2 operatingmodes are aligned to frame and slot timing of the system. The concept ofa frame is used to allow for the definition of transmission slots withinthe system. In a preferred embodiment:

-   -   A frame has duration which is an integral fraction of 60        seconds, and is synchronised to the UTC minute roll-over (for        example, 4 seconds); and    -   Frame timing is based on slots having a duration which is a        multiple of an integer number of symbol periods.

In another embodiment each PHY has a slot period which is equivalent tothe duration of one fixed-length packet transmission interval, includingguard periods.

ST1 Access Method

In an embodiment the ST1 access method employs an uncoordinated slottedALOHA scheme. User terminals transmit packets of a fixed size andcommence transmission on an ST1 slot boundary.

User terminals may access the channel using techniques described inInternational Patent Application No PCT/AU2013/000895.

In the case of satellite reception, due to propagation delay and themotion of the satellite, packets received at the access node may vary intiming offset and frequency offset. In the preferred embodiment ST1packet transmissions will include sufficient unused guard time to allowfor variation in propagation delay.

Synchronised slot times for the ST1 service allow the timing of ST1transmissions received at the access node to be constrained. This isadvantageous for the multi-user signal processing of multipleoverlapping packets as it prevents overlap between slots.

ST2 Access Method

In the preferred embodiment the ST2 Access Method employs a TDMA accessscheme to coordinate access to the channel during a frame period.

The Medium Access Control function operating in the access nodetransmits downlink TDM slot allocation information in each frame period(for the following frame period). It also transmits uplink slotallocation information in each frame period. User nodes/gateway nodesmay request, further transmit slots in packets they send to the accessnode.

A portion of the uplink frame period is reserved for slotted-ALOHAaccess to allow new UNs/GNs to request initial access to the channel.Requests may collide, resulting in lost requests. These will be re-triedby the user nodes/gateway nodes in a later frame.

In the preferred embodiment TDMA frame timing is referenced with respectto UTC time at the access node, and transmissions from usernodes/gateway nodes to the access node include pre-compensation for theeffects of frequency and timing offset. In the preferred embodimentthese parameters are estimated by each UN based upon reception ofpackets from the access node via the ST2-DN downlink.

In the preferred embodiment the access node synchronises itstransmissions with UTC time only. The UN ST2-DN receiver then estimatesand compensates for channel effects such as carrier frequency offset,and timing offset.

Multiple Channel Operation

In one embodiment the system supports multiple channel operation,providing a mechanism for channel frequency agility, and also thepossibility for operation on multiple channels concurrently.Multi-channel operation also allows the system to be implemented in asingle channel operating mode, where the same radio channel is used forboth ST2-UP and ST2-DN links.

When an access node allocates transmission slots to a user node orgateway node, it also identifies the channel on which the slots havebeen allocated.

-   -   All channels available for operation are identified by a unique        channel number; and    -   A channel number to channel frequency map instructs user nodes        which frequency is to be used for each given channel number. The        map may be pre-loaded into the user nodes or announced by the        access node.

Identification And Addressing

In an embodiment all logical nodes within the system are assigned a NodeUnique ID (NUID) which allows them to be unambiguously identified withinthe system. All transmissions by devices within the system include theirNUID. The NUID may also be used to identify the destination of messagesin the system.

In one preferred embodiment the NUID length is 48 bits.

Link Level Authentication

In an embodiment, system authentication mechanisms prevent unauthorisedaccess to the radio channel. Authentication within the Medium AccessControl layer ensures that only those nodes with the appropriatecredentials have access to communication services.

A user/gateway node authentication mechanism proves user node/gatewaynode eligibility for access to the access node with which they aretrying to operate. In an embodiment the channel reservation systememploys a strong authentication method.

In an embodiment authentication operates in both directions, so thatuser nodes and gateway nodes ensure they are communicating with anauthorised access node before initiating data transport.

Message Networking Layer

The Message Networking Layer (MNL) 1206 provides networking andtransport mechanisms for transporting user messages across multiple linklayers between a source and a destination. The MNL may provide thefollowing functionality:

-   -   A Message Transport function, providing network layer protocols        for message transport, which:        -   a. Provides an interface to the Application Layer.        -   b. Provides an interface to the MAC, determining how the            network layer protocols operate over the link layer            interface (MAC).        -   c. In an embodiment an acknowledged delivery service is            provided, where applications are notified of successful            delivery via the network layer interface. Note that these            acknowledgements could be significantly delayed depending            upon the remote location of the applications.    -   A Message Networking function, providing a store and forward        mechanism:        -   a. Routing (including geographic routing) and addressing        -   b. Queuing and scheduling of data for transmission

Message Transport Function

In an embodiment of the present invention, the Message Transportfunction provides:

-   -   A small message service, which maps directly to single link        layer packet unacknowledged message service (UMS) and        acknowledged message service (AMS).    -   A large object transport service for transmitting large data        objects, such as firmware upgrade, images, etc.        -   a. Service uses either the AMS or UMS and provides suitable            fragmentation, re-assembly and re-transmission functions.        -   b. Broadcast/multicast, for example, for transmission of            bulk firmware upgrade images to devices in the field.        -   c. Unicast    -   Transmission of large data objects from remote sensor        applications to corresponding central applications connected to        the CAH.    -   Transmission of large data objects to a specific user node and        application, for example, for single device firmware or        configuration upgrade.    -   Broadcast or multicast of large objects—whole or fragments of        large objects will be stored on access node. In this case the        central application sends an object to the CAH, and the CAH        transmits it to the access node. The access node then transmits        to other nodes using appropriate rules to determine when and        where to transmit, for example, based on geographic routing.        When transmission has completed, the object is removed.    -   Geographic routing, including management of messages sent and        the geographic areas in which they were sent.

In an embodiment, data transfer sessions between the access node anduser nodes/gateway nodes will include exchange of position information,allowing the access node message transport function to make informeddecisions about when to schedule messages for transmission to individualor groups of nodes.

Message Networking Function

In the preferred embodiment a Message Networking function is responsiblefor routing and queuing messages which are in-transit through thesystem, including the following.

-   -   Routing of inbound messages to appropriate queues per        destination, including:        -   a. Messages from user nodes routed to the CAH.        -   b. Messages from CAH may be routed to any node (gateway            node, access node, and typically user nodes).    -   Queuing of messages, based on quality of service (QoS) and/or        user priority status, including:        -   a. User Node queues, for all messages provided by gateway            nodes destined for user nodes.        -   b. Gateway Node queues, for messages from user nodes            destined for the CAH.        -   c. Broadcast and multi-cast transmission queues        -   d. Geographic broadcast queues.    -   Storing messages in queues until they are able to be delivered        (or they expire due to age).    -   Delivery to local applications.

Message Level Security

In an embodiment, authentication is employed for transmitted data,allowing the integrity of received data to be verified. Authenticationis provided by a sufficiently robust and reliable digital signaturemechanism. Authentication of messages provided at theapplication-to-application interface ensures that the receivingapplication can trust that the transmitting application did indeedtransmit the message, and that the message has not been compromised.

In another embodiment the data encryption is provided as an integratedcomponent of the messaging service.

Application Layer

In an embodiment the Application Layer 1208 provides an applicationinterface mechanism through which application programs can register withthe communications system and then access communications and systemmanagement services.

In another embodiment the Application Layer 1208 provides an interfaceto third party protocol stacks (or stack components) that may residebetween the communications system and the application program. In thiscase the application layer may implement an interface that enablessystem access to application programs designed to communicate via thethird party protocol. Third party protocols may include, for example,industry standard protocols such as the Distributed Network Protocol(DNP3) and Modbus.

System Entities

The functional network entities described above may be implementedwithin the physical system entities described in this section. Theentities described in this section may be implemented using fixed orreconfigurable architectures, such as software defined radios (SDR). Inthis respect, an SDR type implementation may allow further benefits,such as, on-board processing, which may lead to improvements forsensing, automation and control not possible with conventional systems.Further, an SDR may be remotely configured or updated, which may allowlower cost bug fixes, upgrades or optimisation. These features areexpected to be particularly advantageous in implementations in which oneor more system entities are remotely deployed, such as space-basedsystems.

Having generally described the role and operation of the system entitiesof an embodiment of the system, the description will now turn to thefunctional architecture of those entities. It is to be noted that thedescription that follows refers to functional views of the systementities which omit details regarding power supply. It is assumed thatthe entities are appropriately powered, either via mains supply and/orbattery and/or solar power.

Node Based System Entities

FIG. 4 is a generic functional block diagram for a node based systementity 400. In the present case, the node based system entities include:

-   -   The user node (UN), which may be implemented within user        terminal (UT) equipment;    -   The gateway node (GN), which may be implemented within gateway        terminal (GT) equipment; and    -   The access node (AN), which may be implemented within any system        entity that is selected to provide a point of access into the        system 300 (ref. FIG. 3).

Examples of a system entity which may provide a point of access into thesystem 300 include:

-   -   Satellite payload in the case of a satellite communications        system;    -   Cellular Base station; or    -   Wireless access point.

FIG. 4 depicts a node including single antenna radio interface 402.However, it is to be noted that the number of antennas and theirconfiguration will depend upon the radio implementation, and that thearchitecture also supports the use of multiple antennas.

As shown in FIG. 4, the node entity 400 includes a node 404, a GPSreceiver 406, providing time and position information to the node 404, acommunications interface 408 (shown here as a IP/Ethernet interface),providing external connectivity to the node 404 and applications, and anapplication environment 410.

The application environment 410 may be used to execute systemapplications. It may also be configured to allow users to executeapplications on the entity, rather than connecting via thecommunications interface 408. The environment provided to a user may beimplemented in an abstract manner that separates it from corefunctionality of the entity thus protecting critical functions such asnode operation in the event of application failure, for example, via oneor more virtual machines.

The node entity 400 may also implement additional features, such as auser interface, further input/output interfaces (for example, USB,RS-232, CAN, or other satellite system bus interface), and an Ethernetswitch.

The node entity 400 may be implemented as a generic device, for example,a generic user terminal that allows users to connect external equipment.Alternatively, the node entity 400 may be a custom implementationaddressing specific requirements, for example, on power, form factor, orcost.

Gateway terminal node entities may be implemented using a low costarchitecture, and may have a similar architecture to that used for userterminal node entities. In this respect, low gateway terminalimplementation cost may present an opportunity to deploy a large numberof gateway terminals. A geographically disperse set of gateway terminalswill provide reduced data latency between central applications andremote terminals, and reduce the storage requirements of the accessnodes in the system 300 (ref. FIG. 3).

Turning now to FIG. 5 there is shown a functional block diagram for aST1RN based system, entity 500 which implements an ST1 recorder node, asdescribed above. As shown, the illustrated ST1 recorder node 500includes a GPS receiver 502, providing time and position information tothe node 500. The node 500 may also include a communications interface504 (shown as an IP/Ethernet interface) providing external connectivityto the Node and Applications, and an application environment 506, asdescribed above. Further input/output interfaces such as USB, RS-232,CAN, or other satellite system bus interface may also be provided. Auser interface may also be provided.

Composite System Entities

In some embodiments, composite system entities may be provided whichcombine the functionality provided by one or more nodes. For simplicity,composite system entities are described here in terms of implementingmultiple nodes. However, the implementation may exploit common featuresof the nodes in order to reduce complexity. For example, a single timeand position service may be shared between two nodes within the samesystem entity.

In some embodiments a multi-mode gateway/access terminal (GAT) isprovided which includes both gateway node and access node functionalityin a terminal entity. A multi-mode gateway/access terminal may beterrestrially located, airborne, or space-based. A multi-modegateway/access terminal may be located at a fixed location or be mobile,for example, on-board a vehicle, vessel, aircraft or spacecraft.

As described for the case of the gateway and access nodes, availabilityof a multi-mode gateway/access terminal connection to the hub 312 may bepersistent or intermittent.

In one embodiment, a multi-mode gateway/access terminal may switch modesbetween providing access node functionality and gateway nodefunctionality. Mode switching may be controlled by the multi-modegateway/access terminal having knowledge of the location of other accessnodes within the system 300 (for example, provided as by the hub 312),and thus making a decision on when to enable and disable the access modeof operation. In some instances, switching may be triggered bycentralised mode control instructions initiated from the hub 312.

A multi-mode gateway/access terminal may detect the presence of a secondaccess node, for example, by periodically listening for announcements onthe radio interface. An access node may then use this knowledge totrigger the mode switch between access node 306 (Ref. FIG. 3) to gatewaynode 308 (ref. FIG. 3). If the multi-mode gateway/access terminalswitches to gateway node mode it becomes a slave to the second accessnode as its master, and vice versa.

In another embodiment a multi-mode gateway/access terminal maysimultaneously provide both access node and gateway node functionality.

Upon detecting each other, multiple multi-mode gateway/access terminalsmay negotiate the use of channel resources (slots) in order to co-existand/or cooperate.

Turning now to FIG. 6 there is shown a first example configurationincluding a multi-mode gateway/access terminal 600 operating in a firstmode. In this example, the multi-mode gateway/access terminal 600operates in an access node mode, providing communications services touser nodes 304 that are in range via the remote radio interface 314. Inthe illustrated example, the multi-mode gateway/access terminal 600 alsohas an active connection to the hub 312, and may use this connection tocommunicate data from the user nodes 304 directly to the hub 312. Themulti-mode gateway/access terminal 600 may also communicate messagesfrom the hub to connected user nodes 304.

In the configuration shown in FIG. 6, if the multi-mode gateway/accessterminal 600 does not have an active connection to the hub 312 it storesdata coming from the user nodes 304 to be transferred to the hub 312 inthe future. The multi-mode gateway/access terminal 600 may also forwardpreviously stored messages from the hub 312 destined for the connecteduser nodes 304.

Referring now to FIG. 7 there is shown a second example configurationincluding a multi-mode gateway/access terminal 600 operating in a secondmode. In this example, the multi-mode gateway/access terminal 600operates in a gateway node mode, providing communications services tothe access node 306 that is in range via the gateway radio interface316. In the illustrated example, the multi-mode gateway/access terminal600 also has an active connection to the hub 312, and may use this toforward data from the access node 306 directly to the hub 312. Themulti-mode gateway/access terminal 600 may also forward messages fromthe hub 312 to the connected access node 306.

In the illustrated configuration, if the multi-mode gateway/accessterminal 600 does not have an active connection to the hub 312, itstores data coming from the access node 306 to be forwarded to the hub312 in the future. The multi-mode gateway/access terminal 600 may alsoforward previously stored messages from the hub 312 that are destinedfor the access node 306, or destined for a user node (to be forwarded bythe AN in the future).

FIG. 8 shows a third example configuration including a multi-modegateway/access terminal 600 operating in a third mode whichsimultaneously provides access node and gateway node functionality. Themulti-mode gateway/access terminal 600 is able to provide communicationsservices to other access node entities (via the gateway radio interface316) and user nodes (via the remote radio interface 314). In the exampleshown, the multi-mode gateway/access terminal 600 has an active hubconnection and may use this to transfer data between the hub 312 andother connected entities.

In the configuration of the third example, as shown in FIG. 8, if themulti-mode gateway/access terminal 600 does not have an activeconnection to the hub 312 it stores data coming from the access node 700to be forwarded to the hub 312 in the future. The multi-modegateway/access terminal 600 may also forward previously stored messagesfrom the hub 608 that are destined for the access node 700, or destinedfor user nodes 602, 604 (to be forwarded by the access node 700 in thefuture).

Turning now to FIG. 9 there is shown a fourth example implementationincluding three multi-mode gateway/access terminals 600-1, 600-2, 600-3.In this example, the three multi-mode gateway/access terminals 600-1,600-2, 600-3 simultaneously provide access node and gateway nodefunctionality and have coordinated access to share channel resources.

Gateway/access terminal 600-3 has an active connection to the hub 312.Gateway/access terminal 600-3 to gateway/access terminal 600-2 andgateway/access terminal 600-2 to gateway/access terminal 600-1communications are provided via the gateway radio interface 316.Gateway/access terminal 600-1 also provides communications services touser nodes 304, via the remote radio interface 314. Through cooperativeconfiguration of gateway/access terminals 600-1, 600-2, 600-3 it ispossible to transfer data, between the hub 312 and other connectedentities through message hopping.

It will be appreciated that although the example illustrated in FIG. 9includes three gateway/access terminals 600-1, 600-2, 600-3, theconfiguration may be extended through the addition of furthergateway/access terminals 600.

Message hopping may also be performed across multiple gateway/accessterminals 600 without requiring simultaneous connectivity as each nodemay implement the earlier described message storage function allowing itto store received messages and forward these messages at a later time.Moreover, while FIG. 9 shows the use of gateway/access terminals 600operating in simultaneous access node and gateway node mode, it ispossible that message hopping may be performed using the accessnode/gateway node mode switching gateway/access terminals describedabove.

Embodiments of the gateway/access terminals may provide the followingbenefits:

-   -   When operating in access mode, the gateway/access terminal can        service communication requirements of user nodes within range.        This may reduce user nodes requirements to communicate with a        second access node when they are within its range, thus reducing        load on the radio channel resource for the second access node;    -   When the gateway/access terminal has an active connection to the        hub and is in access node mode it is able to provide low latency        communication between the hub and the user nodes within range of        the gateway/access terminals; and    -   The gateway/access terminals enables message hopping across        entities.

Composite system entities may be constructed by including multiple nodesinto any system entity. For example, the gateway node and access nodemay be implemented within any system entity that is selected to providea point of access into the system, such as a satellite payload, cellularbase station, or wireless access point. In such cases, the resultingcombination of the access node and gateway node may provide the samebenefits as described for the gateway access terminal.

The Central Host Entity

FIG. 10 shows a functional architecture for the central host 1000 systementity. As shown, the entity 1000 implements a central application hubfunctional network entity 1002, as described above, a timing sourceinput interface 1004 providing time (and potentially position)information, a communications interface 1006 (shown here as anIP/Ethernet interface) providing system and external connectivity. Anoptional application environment 1008 allowing for the execution ofcentral applications may also be provided.

The central application hub 1002 may be implemented in software runningon a computing platform that provides, for example, IP connectivity, forexample, a PC or server platform. The same platform may be used to hostcentral applications.

The timing source input interface 1004 may source information from aGPS. In this case position information may also be provided to thecentral application hub 1002. The timing source input interface 1004 mayalso be provided via the IP network interface, for example, coming froma time server computer.

The central host 1000 may also implement additional features, such as auser interface, further input/output interfaces (for example, USB,RS-232), and an Ethernet switch.

Example Implementation

The following description relates to embodiments of a communicationssystem according to the present invention in the context of a satellitecommunications system.

FIG. 11 shows an example scenario pertaining to a preferred embodimentof the communication system 1100. For clarity, FIG. 11 illustrates onlya small number of system entities, applications, and system users. Thefunctionality of each entity is described above. System entities areshown as solid lined boxes; functional network entities (nodes) asdashed boxes; and applications as ellipses.

In the preferred embodiment, the communications system 1100 includes oneor more satellites in Low Earth Orbit (LEO). Other orbits may also beemployed, such as Medium Earth Orbit (MEO) and Geostationary Earth Orbit(GEO). Moreover, the system 1100 may include multiple satellites, havinga mixture of orbit types.

As will be appreciated by a skilled reader, satellites are equipped withone or more satellite payloads (SP). In the preferred embodiment, thesatellite payload is an access node based system entity, as describedabove. Hence, in the embodiment illustrated in FIG. 11, access node 306is provided as satellite payload equipment. The satellite payloadequipment may also include interfaces to communicate with the satellitesystem, for example, via the system bus.

In the preferred embodiment, radio interfaces 314 and 316 are providedusing UHF and/or VHF spectrum. In the illustrated example the radiointerface 314 correspond to the remote radio interfaces of the typepreviously described, whereas radio interface 316 corresponds to agateway radio interface of the type previously described. It is to beappreciated that the system 1100 may employ multiple radio channels, andmay re-assign their use during operation, as described above.

In one embodiment, radio interface uplink and downlink operationsperformed over the radio interfaces 314, 316 are performed in afull-duplex mode on multiple frequencies. In another embodiment, theuplink and downlink operation are performed on the same frequency viatime division duplex. In another embodiment, the system 1100 is flexibleto allow uplink and downlink time division or frequency division duplexoperation.

The central host 1102 system entity is implemented as described above.In the preferred embodiment a GPS is input as the timing source. Otherembodiments may receive timing information from a networked time servercomputer, as previously described.

As shown, the central host 1102 includes the central application hub1104, and also provides a system monitoring and control application1106. In this example, the system monitoring and control application1106 provides the central application programs (CA) to the system nodemanagement applications. System nodes may run node managementapplications, as previously described.

In the embodiment shown, each node runs the firmware upgrade service(FWUS) and remote management service (RMS) also as described above.

In the preferred embodiment, one or more gateway terminals 1108, 1110are connected to the central host 1102 via a suitable communicationsinterface which may include an Ethernet/IP connection. In the presentcase, gateway terminal 1108 is connected to an electronically controlledsteerable antenna mount 1112. The gateway node 1114 of the gatewayterminal 1108 determines the location of the access node 306 fromincoming access node announcement messages, and forwards thisinformation to an antenna steering application 1116 running on thegateway terminal 1108. The application 1116 then extracts positioninformation for the access node 306 and directs the antenna 1112 inorder to maximise link quality. In another embodiment a gateway terminalmay employ one or more omnidirectional antennas.

In other embodiments, applications may run on external devices that areconnected to the gateway terminals 1108, 1110. Connection betweengateway nodes 1114, 1118 and the central application hub 1104 may not bepersistent, as described above.

Gateway terminals 1108, 1110 communicate with the access node 306 viathe gateway radio interface 316. In the preferred embodiment the gatewayradio interface 316 is provided by a Service Type 2 (ST2) bi-directionalradio interface. Other embodiments may provide the gateway radiointerface 316 via alternate means, as described above.

The access node 306 shown in FIG. 11 runs a file transfer access nodeapplication, as described above.

User terminals 1120, 1122, 1124 communicate with the access node 306 viathe remote radio interface 314. In the preferred embodiment the remoteradio interface 314 includes both a Service Type 1 (ST1) unidirectionalradio interface and a Service Type 2 (ST2) bi-directional radiointerface. However, it is to be appreciated that other embodiments mayprovide only one of these interfaces.

Three user terminals 1120, 1122, 1124 are shown in FIG. 11. Userterminals 1120, 1122 communicate with a respective user device 1126,1128, 1130. In the present case, user device 1126, 1128, 1130 to userterminals 1120, 1124 connections are provided using an Ethernet/IPcommunication interface. However, other suitable communicationinterfaces may be employed. Suitable communication interfaces would bewell within the knowledge of a skilled addressee.

In the case of user device 1126, a remote application program on theuser device 1126 is executed to provide file transfer services, asdescribed above, and forwards the file to the connected user terminal1120. User device 1126 uses the ST2 service to support this service. Thecorresponding central application is connected to the centralapplication hub 1104 via the central host 1102.

User terminal 1122 allows multiple user devices 1128, 1130 to interfaceto user node 1132 via, for example, an Ethernet switch. In this example,two sensor user devices (“User Device 1” and “User Device 2”) areconnected, each running a remote sensing remote application as describedabove. User terminal 1122 may use the ST2 service to support thisapplication; or the ST1 service if feedback is not required from theassociated central application 1134 to the remote sensing remoteapplication program on user devices 1128, 1130. In the present case, thecorresponding remote sensing central application 1134 is connected tothe central application hub 1104 via the central host 1102.

In the illustrated example, the user terminal 1124 executes a positionreport remote application 1136 that allows the corresponding centralapplication 1138 to report the position of this terminal (and otherslike it) to a user (“User 3”). User terminal 1124 may use either the ST1or ST2 service to support this application.

In the preferred embodiment gateway access terminals are also deployedin regions where user terminals are expected to be in range, eitherpermanently or momentarily. The connection between gateway accessterminals and the central application hub 1104 may be persistent orintermittent, as described above. Gateway access terminals may employone or more directional or omnidirectional antennas, or a combination ofone or more directional or omnidirectional antennas. In one embodiment,the gateway access terminal employs one or more directional antennas forthe gateway radio interface when providing gateway node functionality,and one or more omnidirectional antennas for the remote radio interfacewhen providing access node functionality. In another embodiment thegateway access node employs one or more omnidirectional antennas tosupport both remote and gateway radio interfaces. The use ofomnidirectional antennas offers potential benefits of reduced systemcost, deployment and maintenance requirements.

In another embodiment a geographically disperse set of gateway terminalsand/or gateway access terminals is deployed in order to increase theduration of connectivity between gateways and satellite payloads, andreduce data transfer latency between the central host 1102 and othersystem entities.

In another embodiment, when in range of both ST2 User Terminal andGateway Node, the satellite may operate in two-way mode, eitherregenerative, or bent-pipe.

In another embodiment access node based system entities may be deployedterrestrially, or be airborne, in order to service user terminals. Theconnection between access nodes and the central application hub 1104 maybe persistent or intermittent, as described above.

In the preferred embodiment system entities are implemented using fullyor partially reconfigurable devices, such as software defined radios,that are capable of supporting multiple applications and multiplefrequency bands. In other embodiments, fixed architecture devices may beused.

In another embodiment, the access node (which in this case is thesatellite payload) is a Service Type 1 Recorder Node (ST1RN) basedsystem entity as described above. In this case the ST1 service isimplemented by receiving and recording the ST1 Remote Radio Interfacechannel using the ST1RN. The recorded channel data is then transmittedto the ground via the Gateway Radio Interface. Digital signal processingof the channel data is then performed, and resulting messages areforwarded to the central application hub 1104.

In another embodiment the satellite payload includes both the accessnodes and ST1RN nodes, allowing it to process data while in orbit and/orrecord channel samples for ground based processing.

In another embodiment the satellite payload includes an access node andgateway node entity. In this embodiment the satellite may be able tosupport message hopping, as described above for the case of a gatewayaccess terminal (which also implements both access node and gatewaynode). In this embodiment inter-satellite-links (ISLs) may be formed. Inanother embodiment the GM is implemented to be compatible with a thirdparty satellite service provider, thus allowing such services to be usedto link the space and ground segments of the described architecture.

The described embodiments may also include the authentication andsecurity services as described above.

Compact Antenna

Applications such as tracking and sensing, may require a small formfactor terminal implementation, thus requiring a compact antenna.

In a preferred embodiment the compact antenna is a coil of conductivemetal having total length equal to one quarter of the wavelength at thetransmit frequency. The coil may in one embodiment be constructed fromwire of a variety of alloys but may also be of gold or other suitablyconductive single element, or in another be manufactured onto a printedcircuit board using the conductive circuit track material on the boardas the antenna element.

In a preferred embodiment, the antenna is fed at an end of the antenna.The preferred feed end is located at the centre of a coil having aspiral shape in a single plane.

In a preferred embodiment a ground plane is used that has similar areadimension to the coil located in a plane parallel to the plane of theantenna.

During deployment (positioning of) the terminal is such that theelectrically conductive surface of the ground plane is located facingaway from the intended direction of radiation. For example, in the caseof a satellite system the antenna associated with the terminal is bestoriented such that the ground plane is on the Earth side of the in orbitsatellite. The flat coil antenna including the ground plane enables theassociated terminal (including the antenna) to have a compact tag-likeform factor.

In a preferred embodiment, labelled Case-A, for a transmit frequency of162.725 MHz the length of the coil is approximately 46 cm. The coilconsists of between 1 and 4 self-enveloping loops, with side dimensionsacross the substantially planar coil formation being in one embodimentapproximately 4.5 cm by 6.5 cm.

A short section of the feed portion of the antenna connects the coil,between the feed point located generally central to the planar coil tothe edge region of the planar coil. The feed portion of the antenna runsat an angle (labelled a in FIG. 13) of approximately 45 degrees to theside of the planar coil. The feed portion is separated from theconductive plane of the coil so as not to make contact with any part orportion of the coil, as can be seen from the top view in FIG. 13. Thefeed portion is connected between the free end of the depending part ofthe coil and the centre conductor of a co-axial cable located near oneof the sides of the planar coil. As described above the ground plane hassimilar planar dimension to the coil and is mounted in the same plane asthe coil, and connected to the shield (outer conductor) of the coaxialcable. The co-axial cable is used to feed radio frequency signal to theantenna.

An embodiment of the compact antenna described above is depicted in FIG.13 (front and top down views).

In another embodiment, one end of the antenna structure begins at thecentre of the coil, and the signal feed is connected to the antenna atthis point. The ground plane again has similar dimensions as the coil.The ground plane is mounted such that the plane of the antenna and theplane of the ground plane are parallel with a physical separationbetween the coil and the ground plane. The outer shield of the coaxialcable is connected to the ground plane. A predetermined separationbetween the coil and ground plane is provided, with separation distancedepending upon the permittivity of the medium located between the twoplanes and the frequency of operation of the antenna. In one embodiment,that of free space, the distance may be of the order of 1 to 2 cm. Inanother embodiment the space may be used to house components of theterminal, thus changing the permittivity. This embodiment of the compactantenna is shown in FIG. 14 (front and top down views).

In order to compare the performance of the compact antennas describedabove to that of some commercial off-the-shelf monopole antennas, anexperiment was conducted during which several collocated prototypeterminals were setup to transmit to a satellite in low earth orbit.Packets were transmitted using the ST1-PHY described above. The transmitfrequency was 162.725 MHz and the terminal output power was 32 mW (15dBm). FIG. 15 shows a spectrogram of the signal received at thesatellite during a single time slot of 250 ms duration. Packets weresuccessfully received from 9 terminals, and each packet shown indicatesthe terminal identifier along with the received SNR (measured/estimated)in dB. Terminal 02 was used with the antenna depicted in FIG. 14 being acompact antenna orientated horizontally. Terminal 03 used an antenna asdepicted in FIG. 13 being a compact antenna orientated vertically.Terminal 04 also used an antenna as disclosed in FIG. 13 being a compactantenna orientated vertically, however rotated in azimuth by 90 degreeswith respect to the antenna used by Terminal 03. The other terminalsused off-the-shelf monopole antennas. The test results as illustrated inFIG. 15 show that SNRs measured for packets received from the compactantennas were similar to, or greater than, SNRs measured for theoff-the-shelf monopole antennas.

The tests described were conducted in the VHF band at 162.725 MHz. Theantenna design is also expected to be applicable to other frequencies,including other VHF frequencies, and frequencies in the UHF band. Asdescribed above the antenna may be tuned to a particular frequencythrough selection of the coil length. The coil length is chosen to beequal to one quarter of the wavelength, hence it is expected that higherfrequencies will permit more compact antenna dimensions.

Throughout the specification and the claims that follow, unless thecontext requires otherwise, the words “comprise” and “include” andvariations such as “comprising” and “including” will be understood toimply the inclusion of a stated integer or group of integers, but notthe exclusion of any other integer or group of integers.

The reference to any prior art in this specification is not, and shouldnot be taken as, an acknowledgement of any form of suggestion that suchprior art forms part of the common general knowledge.

It will be appreciated by those skilled in the art that the invention isnot restricted in its use to the particular application described.Neither is the present invention restricted in its preferred embodimentwith regard to the particular elements and/or features described ordepicted herein. It will be appreciated that the invention is notlimited to the embodiment or embodiments disclosed, but is capable ofnumerous rearrangements, modifications and substitutions withoutdeparting from the scope of the invention.

1. A communication system, including: a user node for receiving datafrom a remote application program, the data including message data forcommunication to a central application program operatively associatedwith the remote application program; a plurality of geographicallydistributed gateway nodes; one or more access nodes for receiving themessage data from the user node via a first communications interface,and communicating the message data via a second communications interfaceto one or more of the plurality of geographically distributed gatewaynodes; and a hub for communicating with the one or more of the pluralityof geographically distributed gateway nodes to receive the message datafor communication to the central application program.
 2. A communicationsystem according to claim 1 wherein at least one of the plurality ofgeographically distributed gateway nodes and the user nodes are lowpower nodes.
 3. A communication system according to claim 2 wherein thelow power nodes have an EIRP of less than 5 W.
 4. A communication systemaccording to claim 1 wherein at least one of the first communicationsinterface and the second communications interface share the samefrequency band and is one of a VHF band interface or a UHF bandinterface.
 5. (canceled)
 6. (canceled)
 7. A communication systemaccording to claim 1 wherein at least one of the plurality ofgeographically distributed gateway nodes and the user node isreconfigurable as an access node to support communication services withat least one of one or more other gateway nodes and user nodes.
 8. Acommunication system according to claim 1 wherein the remote applicationprogram includes a sensor network application program, and wherein themessage data includes sensor data from one or more sensors of a sensornetwork in communication with the remote application program.
 9. Acommunications system according to claim 1 wherein at least one of theone or more access nodes further comprising: a satellite based accessnode; a cellular base station; or a wireless access point.
 10. Acommunications system according to claim 1 wherein the user node storesthe message data received from the remote application program when theone or more access nodes are not available for communication with theuser node, and transfers the stored message data to one or more of theaccess nodes when available for communication with the user node.
 11. Acommunications system according to claim 1 wherein the access nodestores the message data received from the user node when none of the oneor more geographically distributed gateway nodes are available forcommunication with the access node, and transfers the stored messagedata to at least one of the one or more geographically distributedgateway nodes when available for communication with the access node. 12.A communications system according to claim 11 wherein the access nodeincludes an application program which is executable to manipulate themessage data received from the user node, and wherein the message datacommunicated to the one or more of the plurality of geographicallydistributed gateway nodes includes manipulated message data.
 13. Acommunications system according to claim 1 wherein at least one of theone or more access nodes, the user node, or one of the geographicallydistributed gateway nodes includes a software defined radio. 14.(canceled)
 15. (canceled)
 16. A communication system comprising: acentral application program operatively associated with one or moreremote application programs; a user node for providing data to theremote application program; a plurality of geographically distributedgateway nodes; a hub for receiving data from the central applicationprogram for communication to the one or more remote application programsand communicating the received data to a selected one or more of theplurality of geographically distributed gateway nodes; and one or moreaccess nodes for receiving the data from the selected one or more of thegeographically distributed gateway nodes using a first communicationsinterface, and communicating the received data to the user node for theone or more remote application programs using a second communicationsinterface.
 17. A communication system according to claim 16 wherein atleast one of the geographically distributed gateway nodes and the usernode are low power nodes.
 18. A communication system according to claim17 wherein the low power nodes have an EIRP of less than 5 W.
 19. Acommunication system according to claim 16 wherein at least one of thefirst communications interface and the second communications interfaceshare the same frequency band and is one of a VHF band interface or aUHF band interface.
 20. (canceled)
 21. (canceled)
 22. A communicationsystem according to claim 16 wherein at least one of the geographicallydistributed gateway nodes and user node is reconfigurable as an accessnode to support communication services with at least one of the one ormore other geographically distributed gateway nodes and user nodes. 23.(canceled)
 24. (canceled)
 25. (canceled)
 26. A communications systemaccording to claim 16 wherein the at least one of the one or more accessnodes further comprising: a satellite based access node; a cellular basestation; or a wireless access point.
 27. A communications systemaccording to claim 16 wherein the selected one of the geographicallydistributed gateway nodes is selected by the hub according togeographical information associated with each of the one or moregeographically distributed gateways and each of the one or more accessnodes to reduce latency.
 28. A communications system according to claim27 wherein the selected one of the geographically distributed gatewaynodes is selected by the hub to manage load balance.
 29. A communicationmethod comprising: a user node receiving data from a remote applicationprogram, the data including message data for communication to a centralapplication program operatively associated with the remote applicationprogram; one or more access nodes receiving the message data from theuser node via a first communications interface, and communicating themessage data via a second communications interface to one or more of aplurality of geographically distributed gateway nodes; and a hubcommunicating with one or more of the plurality of geographicallydistributed gateway nodes to receive the message data for communicationto the central application program.
 30. (canceled)
 31. (canceled) 32.(canceled)
 33. (canceled)
 34. A communication method comprising:providing a plurality of geographically distributed gateway nodes;receiving data by a hub, from a central application program forcommunication to one or more remote application programs andcommunicating the received data to a selected one or more of theplurality of geographically distributed nodes; one or more access nodesreceiving data from the selected one or more of the geographicallydistributed gateway nodes using a first communications interface, andcommunicating the received data to the one or more remote applicationprograms using a second communications interface.
 35. A method accordingto claim 34 wherein the one or more access nodes includes a satellitebased access node.
 36. A method according to claim 34 wherein theselection of the geographically distributed gateway node is based ongeographical information indicating an actual or expected geographicalposition of the one or more access nodes.
 37. A communication systemaccording to claim 1 wherein at least one of the first communicationsinterface and the second communications interface operates at less than1 GHz and are substantially the same interface.
 38. (canceled)
 39. Acommunication system according to claim 1 wherein each of the pluralityof geographically distributed gateway nodes includes at least oneomnidirectional antenna.
 40. A communication system according to claim 1wherein the geographically distributed gateway nodes and the accessnodes are connected directly to the hub via at least one of the firstcommunications interface and the second communications interface. 41.(canceled)
 42. (canceled)
 43. (canceled)
 44. (canceled)
 45. Acommunication system according to claim 1 further comprising one or moreprotected application environments for running at least one of theremote application program and the central application program.
 46. Acommunication system according to claim 1 further comprising: a protocolstack structure further comprising: a Physical Layer (PHY); a MediumAccess Control layer (MAC); a Message Networking Layer (MNL); and anApplication Layer.